home *** CD-ROM | disk | FTP | other *** search
- Date: 10 May 1993 10:09:16 -0500
- From: "Tom Scott" <Tom_Scott@qmengr.mail.cornell.edu>
- Subject: MacTCP Problem solved
-
- MacTCP Problem solved
- I feel silly! The overwhelming response to the MacTCP 1.1 with System 7.1 was:
- use MacTCP 1.1.1; System 7.1 *REQUIRES* MacTCP 1.1.1.
-
- I upgraded my IIcx about 3 months ago and I forgot about upgrading MacTCP to
- 1.1.1 when I was setting up these new machines. I've also been embroiled in
- mucho network problemos, so I didn't have time to remember such a *TRIVIAL*
- fact! ;-)
-
- Thanks to all of the following that responded:
-
- Kristi Aho (kaa1@cornell.edu)
- J.Sawers@uts.edu.au (James Sawers)
- Peter Macdonald <pdmmac@mcmail.cis.mcmaster.ca>
- shiekh@ictp.trieste.it (Andy Shiekh)
- "Allan M. Bloom" <IRBLOOM@VTVM1.CC.VT.EDU>
- mcs2@cornell.edu (Wagner Truppel)
- Tom Young <XMU@CORNELLC.cit.cornell.edu>
- msphil@mail.wm.edu (Mike Phillips)
- wmiller@uclink.berkeley.edu (Wayne Miller)
- King Rhoton <king@acpub.duke.edu>
- "Keith Boncek" <keith_boncek@QMRELAY.MAIL.CORNELL.EDU>
- Mark McNair <mcnair@flymo.cac.washington.edu>
- Jeff Luck <JFL4@PSUVM.PSU.EDU>
- mmccarty@HUSKY1.STMARYS.CA (Mike McCarty)
- "Maureen Fisher" <maureen_fisher@QMRELAY.MAIL.CORNELL.EDU>
- HELP DESK <SHDX@CORNELLC.cit.cornell.edu>
- Phillip Corchary <philc@uswmrg5.mrg.uswest.com>
- "Guy DiPietro" <guy_dipietro@qmrelay.mail.cornell.edu>
- ehfm@midway.uchicago.edu (Eric Hoffmann)
- "Duckenfield,Paul" <DUCKENFI@AC.GRIN.EDU>
- mph2@cornell.edu (Matthew Hagopian)
- Fearghas McKay <fearghas@challis.demon.co.uk>
- silber@TC.Cornell.EDU (Jeffrey A. Silber)
- RICHARD LIM <RTL@siva.bris.ac.uk>
- Brent Martin <martin@cc2smtp.emr.ca>
- dwv@magic.ucsb.edu (David Valentine)
-
- And a special thanks to "Kevin Eric Saunders" <saunders@nmc.cit.cornell.edu>,
- who provided me with the MacTCP 1.1.1 specs:
-
- ---
- Release Notes for MacTCP v1.1.1
- Copyright 1992, Apple Computer, Inc.
- All rights reserved.
- August 14, 1992
-
- MacTCP v1.1.1 is an update release for MacTCP v1.1. It includes the
- following improvements:
-
- The number of recognized host file entries is significantly increased.
-
- When an AddrToStr procedure is called with a string of size 16 char and a
- full IP address (an IP address containing all 3 digit numbers such as
- 123.123.123.123), an extra byte is no longer overwritten.
-
- When used over AppleTalk Remote Access, MacTCP handles AppleTalk
- transition events properly.
-
- DNR does not leak memory.
-
- ARP responses are returned for 802.3 ARP requests.
-
- ICMP echo requests no longer crash 68000-based Macintosh computers.
-
- TCP connections are maintained over slow speed or long delay connection
- paths.
-
- UDP Multiport Read returns the correct values for the destination port
- and address.
-
- CMU BootP compatibility is supported.
-
- On links of a transitory nature such as SLIP and PPP, MacTCP initializes
- correctly by resending BootP requests on the open transition event from the
- LAP.
-
- The UDP ASR routine in UDPMultiPortCreate is no longer overwritten.
-
- Performance on Mac Plus computers running System 7.0.x is increased.
-
- TCPSend works correctly on AppleTalk connections to sites that have
- disappeared and reappeared on the network.
-
- The MacTCP control panel shows all available AppleTalk link icons.
-
- Packets are no longer dropped when time to live equals 1.
-
- Pre-AppleTalk Phase 2 Ethernet drivers are supported.
-
-
- IN ADDITION:
- For server based addressing, when switching between data links in the
- MacTCP control panel, set the default gateway address to 0.0.0.0 to assure
- that the gateway address is subsequently obtained correctly.
-
- In low memory situations, high traffic, high transmission rate
- connections can experience data loss problems. These problems can be
- avoided if applications give MacTCP enough memory to work correctly.
-
- Application developers should be sure to consider the following when making
- memory calculations:
-
- - Network MTU size affects the amount of memory needed to receive
- fragmented datagrams. Assume that fragmented packets may be received.
-
- - An application's packet usage may vary from typical expectations. For
- instance, although telnet applications are mostly used in character
- operations, some applications send full size datagrams to telnet consoles.
- Such usage may break connections if applications don't allocate enough
- memory for MacTCP.
- Mark Fleming,
- Macintosh & Network Support, Office System
- Computing & Communications Services,
- Queen's University at Kingston,
- Ontario, Canada, K7L 3N6
-
-
-
- Again, thanks to all who supplied help! Who said there's no net response to
- questions anymore! :-)
-
-
- Thomas Scott, Systems Manager, College of Engineering
- Cornell University, Carpenter Hall Annex, Ithaca, NY 14853
-
-
-
-
-
-